home *** CD-ROM | disk | FTP | other *** search
- Path: itssrv1.ucsf.edu!usenet
- From: Karl Young <kyoung@itsa.ucsf.edu>
- Newsgroups: comp.lang.c++,comp.lang.idl-pwave,comp.programming
- Subject: C++, IDL design question
- Date: Tue, 30 Jan 1996 15:46:09 +0000
- Organization: UCSF, ITS
- Message-ID: <310E3D41.CBB@itsa.ucsf.edu>
- NNTP-Posting-Host: shiva-lr2-2.ucsf.edu
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0b5 (WinNT; I)
- CC: kyoung@itsa.ucsf.edu, maudsle@itsa.ucsf.edu
-
- I'm just starting the design of some medical imaging
- software. The lab I'm at has decided that using IDL
- will make code more usable among collaborators (there
- is currently a mountain of fairly unreadable C that
- will probably have to be rewritten) On the other hand,
- from my limited experience with C++ (just some coding;
- i.e. no extensive design experience) the project seems
- to scream out to be written in C++.
-
- So my question is; does it sound reasonable to design
- the project (Booch diagrams and whatever else...) to
- be coded up in C++ but allow a lot of the called functions
- to be written in IDL (e.g. the interface code and image
- processing stuff) ? (Ideally this should allow for fast
- prototyping, via IDL, and then perhaps recoding of the time
- critical stuff) Has anybody done anything like this and
- been happy/horrified with the results ?
-
- My second question is that since a lot of this code will
- be expected to run on Unix workstations (Sparcs and
- Alphas) as well as PC's, does anybody know of any good
- development enviorenments (e.g. something like the Centerline
- products) that have versions that run on (or can at least
- generate code for) Unix and PC platforms ?
-
- I realize that these are pretty vague and general questions;
- thanks in advance for any comments or advice,
-
- -- Karl Young (kyoung@itsa.ucsf.edu)
-